Security and firewall settings

Firewall settings

Sage 200 runs a variety of programs and services that can be affected by your security and firewall settings.

Sage 200 needs to access certain ports and URLs, so you may need to grant access to these in your security settings.

Access to URLs

You will need to allow access to these URLs, all using HTTPS.

• app.sage200.co.uk

• id.sage.com

• signin.sso.sage.com

• shop.sage.co.uk

• pros200appaproduct.blob.core.windows.net

• www.google-analytics.com

• ssl.google-analytics.com

• pros200appasage.blob.core.windows.net

  Used for e-banking or the nominal link between Sage 200 and Sage Payroll.

• regulatory-reports.sagecompliance.com

  Used for VAT submissions (MTD).

• www.sagetokenservice.com

  Used for Sage bank feeds.

• eu.sagebankdrive.com

  Used for Sage bank feeds.

• api-money.sage.com

  Used for Invoice Payments.

• sandbox.opayo.eu.elavon.com

  Used for Opayo (formerly Sage Pay).

• live.opayo.eu.elavon.com

  Used for Opayo (formerly Sage Pay).

• www.elavon.co.uk

  Used for Opayo (formerly Sage Pay).

Application files

If you control and restrict the applications that can be run in your environment, you will need to allow certain application files to run for Sage 200 and its utilities.

Application files required for Sage 200